Configure Cilium agents to connect to apiserver explicitly #365
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
dghubble
added a commit
to poseidon/typhoon
that referenced
this pull request
Aug 28, 2023
* Cilium v1.14 seems to have problems reliably accessing the apiserver via default in-cluster service discovery (relies on kube-proxy instead of DNS) after some time * Configure Cilium agents to use the DNS name resolving to the cluster's load balanced apiserver and port. Regrettably, this relies on external DNS rather than being self-contained, but its what Cilium pushes users towards
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Workaround for cilium/cilium#27982